[INFO] fetching crate trillium-macros 0.1.0...
[INFO] fixing trillium-macros-0.1.0 against try#622891a4e29178280638a6b63a8908bde2c0c854+cargoflags=-Zfix-edition=start=2015 for pr-157817-2
[INFO] extracting crate trillium-macros 0.1.0 into /workspace/builds/worker-0-tc1/source
[INFO] started tweaking crates.io crate trillium-macros 0.1.0
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate trillium-macros 0.1.0
[INFO] tweaked toml for crates.io crate trillium-macros 0.1.0 written to /workspace/builds/worker-0-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate trillium-macros 0.1.0 on toolchain 622891a4e29178280638a6b63a8908bde2c0c854
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate trillium-macros 0.1.0 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/source:/opt/rustwide/workdir:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:3a6becf2bc8dde7f3fa57ede90e4f284e72d296796fc446bbb1e2c7cc0530151" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] 102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44
[INFO] running `Command { std: "docker" "start" "102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=" "-e" "RUSTDOCFLAGS=" "-w" "/opt/rustwide/workdir" "--user" "0:0" "102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fix" "--allow-no-vcs" "--allow-dirty" "--frozen" "--all" "--all-targets" "--message-format=json" "-Zfix-edition=start=2015", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.106
[INFO] [stderr]     Checking unicode-ident v1.0.24
[INFO] [stderr]     Checking parking v2.2.1
[INFO] [stderr]     Checking futures-core v0.3.32
[INFO] [stderr]     Checking fastrand v2.4.1
[INFO] [stderr]    Compiling quote v1.0.45
[INFO] [stderr]     Checking futures-io v0.3.32
[INFO] [stderr]     Checking futures-lite v2.6.1
[INFO] [stderr]     Checking syn v2.0.117
[INFO] [stderr]     Checking trillium-macros v0.1.0 (/opt/rustwide/workdir)
[INFO] [stdout] error[E0432]: unresolved import `trillium_http`
[INFO] [stdout]  --> tests/transport.rs:5:5
[INFO] [stdout]   |
[INFO] [stdout] 5 | use trillium_http::Synthetic;
[INFO] [stdout]   |     ^^^^^^^^^^^^^ use of unresolved module or unlinked crate `trillium_http`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium_http`, use `cargo add trillium_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `trillium_server_common`
[INFO] [stdout]  --> tests/transport.rs:7:5
[INFO] [stdout]   |
[INFO] [stdout] 7 | use trillium_server_common::{AsyncRead, AsyncWrite, Transport};
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]  --> tests/derive.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 | use trillium::{Conn, Handler, Info, Status::Ok};
[INFO] [stdout]   |     ^^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `trillium`
[INFO] [stdout]  --> tests/derive.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 | use trillium::{Conn, Handler, Info, Status::Ok};
[INFO] [stdout]   |     ^^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `trillium_testing`
[INFO] [stdout]  --> tests/derive.rs:6:5
[INFO] [stdout]   |
[INFO] [stdout] 6 | use trillium_testing::{TestServer, harness, test};
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `trillium_testing`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium_testing`, use `cargo add trillium_testing` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium_server_common` in this scope
[INFO] [stdout]    --> tests/transport.rs:73:48
[INFO] [stdout]     |
[INFO] [stdout]  73 |         #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 113 |     define_transport_with_except!(OuterTransport);
[INFO] [stdout]     |     --------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium_server_common` in this scope
[INFO] [stdout]    --> tests/transport.rs:73:48
[INFO] [stdout]     |
[INFO] [stdout]  73 |         #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 128 |     define_transport_with_except!(OuterTransport, except = set_linger);
[INFO] [stdout]     |     ------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]   --> tests/derive.rs:35:14
[INFO] [stdout]    |
[INFO] [stdout] 35 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium_server_common` in this scope
[INFO] [stdout]    --> tests/transport.rs:73:48
[INFO] [stdout]     |
[INFO] [stdout]  73 |         #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 143 |     define_transport_with_except!(OuterTransport, except = [set_nodelay, peer_addr]);
[INFO] [stdout]     |     -------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium_server_common` in this scope
[INFO] [stdout]    --> tests/transport.rs:73:48
[INFO] [stdout]     |
[INFO] [stdout]  73 |           #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                  ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 158 | /     define_transport_with_except!(
[INFO] [stdout] 159 | |         OuterTransport,
[INFO] [stdout] 160 | |         except = [set_linger, set_nodelay, set_ip_ttl, peer_addr],
[INFO] [stdout] 161 | |     );
[INFO] [stdout]     | |_____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `trillium-macros` (test "transport") due to 6 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]   --> tests/derive.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(Handler, Clone)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]   --> tests/derive.rs:71:14
[INFO] [stdout]    |
[INFO] [stdout] 71 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]   --> tests/derive.rs:82:14
[INFO] [stdout]    |
[INFO] [stdout] 82 |     #[derive(Handler, Clone)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]   --> tests/derive.rs:97:14
[INFO] [stdout]    |
[INFO] [stdout] 97 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:115:14
[INFO] [stdout]     |
[INFO] [stdout] 115 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:119:14
[INFO] [stdout]     |
[INFO] [stdout] 119 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:128:14
[INFO] [stdout]     |
[INFO] [stdout] 128 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:135:14
[INFO] [stdout]     |
[INFO] [stdout] 135 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:141:14
[INFO] [stdout]     |
[INFO] [stdout] 141 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:151:14
[INFO] [stdout]     |
[INFO] [stdout] 151 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:166:14
[INFO] [stdout]     |
[INFO] [stdout] 166 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:179:16
[INFO] [stdout]     |
[INFO] [stdout] 179 |     assert_eq!(trillium::Handler::name(&handler), "custom name (handler)");
[INFO] [stdout]     |                ^^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `trillium` in this scope
[INFO] [stdout]    --> tests/derive.rs:185:14
[INFO] [stdout]     |
[INFO] [stdout] 185 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `trillium-macros` (test "derive") due to 17 previous errors
[INFO] running `Command { std: "docker" "inspect" "102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44", kill_on_drop: false }`
[INFO] [stdout] 102444760c3095ee9db5cb0fb6da31f427e6633f2007e48c5f52b59745789b44
